An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

Hi everyone, I’m looking for some clarification regarding Privacy Manifest requirements (PrivacyInfo.xcprivacy) after resolving a validation issue on my latest submission. In my previous build, I ran into an issue related to NSPrivacyTracking and NSPrivacyTrackingDomains. I updated the manifest to ensure NSPrivacyTracking is set to <true/> alongside our App Tracking Transparency (ATT) prompt, and restricted NSPrivacyTrackingDomains strictly to the required ad service endpoints (googleadservices.com, googlesyndication.com, doubleclick.net, etc.), removing any broad domains. I have just submitted the corrected build: • App Name: Girls vs Boys Tapping • Version: 1.1.2 • Build: 112 • Apple ID: 6809284204 • Status: Waiting for Review Since this is my first time submitting with the updated privacy manifest format after resolving that error, my question is: Once the build enters the review queue with these specific tracking domains and ATT configured, does App Review require any additional documentation in the review notes regarding the ad network tracking domains, or is the .xcprivacy file inside the bundle sufficient for automated validation and review? Just want to make sure everything is 100% in order so there are no unexpected hold-ups while it's in the queue. Thanks in advance for any insights!

I am trying to add testers to External Tester groups for a couple of our iOS apps and after adding them it shows "No Builds Available". This is despite the app being available to that External Tester group with other people having already installed the latest version of the app which is "Available" and not expired. Can someone please fix this? It is so frustrating the number of times I try and release apps to TestFlight and there's some issue blocking me, completely out of my control and I have to rely on someone at Apple fixing something on this terrible AppStoreConnect system.

Hello everyone, I’m looking for advice from developers who have experienced a similar App Store rejection under Guideline 5.6 – Developer Code of Conduct. My app is called Al-Saqar. It is a specialized marketplace and auction platform for falconry enthusiasts. The app includes: Falcon listings and physical product sales Falcon food and accessories Real-world falcon auctions Live auction viewing and bidding Falcon farms and clinics directory Search and filtering User accounts and account deletion All products and auction items are physical goods. There are no digital goods or subscriptions being sold through the app. For auctions, users can view the auction and watch the bids. To participate, they need to complete identity verification and pay a security deposit. The deposit and final payment are handled outside the app through our support team and bank transfer because these are real-world, high-value transactions. Apple rejected the app under Guideline 5.6 with the following message: “We've identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process.” The problem is that Apple did not identify which feature, screen, account state, or behavior they believe was hidden. There are no hidden features intended to be shown only to normal users. The functionality available to users is the same functionality available during review. I have already tried to clarify this with Apple and provided additional information and a screen recording demonstrating the functionality on a real device. I have also submitted an App Review Board appeal, but I am still trying to understand what could be triggering this rejection. Another thing I noticed is that the review appears to have happened extremely quickly, which makes me wonder whether some automated detection or account/runtime behavior could be involved. I obviously cannot confirm that this is the case. I have been trying to publish this app since August 18, 2026, and I have now reached a point where I don't know what I should actually change because Apple has not identified the specific issue. Has anyone experienced this exact Guideline 5.6 rejection, especially the wording about: “features that appear to have been intentionally hidden during the review process” and successfully resolved it? If so, I would really appreciate knowing: What was actually causing the rejection? Did Apple eventually identify the specific feature or behavior? Was it related to remote configuration, server-side logic, feature flags, account states, device/region checks, dynamic content, or third-party SDKs? Did contacting Apple Support or requesting an App Review appointment help? Did you need to submit an appeal, or did a new build eventually resolve the issue? I am not looking to bypass App Review. I simply want to understand what Apple is detecting so I can fix the actual problem instead of making random changes and repeatedly submitting builds. Any experience or advice from developers who have gone through the same situation would be greatly appreciated. Thank you.

My game was submitted for app review for few round, every time they rejected and i resolve the issue, but latest they reject as Guideline 4.3(a) - Design - Spam and dont have response more than 1 week, I am confusing, early stage was Code of developer (showing what my game have with recording),later follow by some bug fix, then design copy-cat ( the game is totally written by me), but then i asked many round please pin point which part. End up they reject with "Guideline 4.3(a) - Design - Spam" and i replied with full list of unique feature my game have and explaination on some feature where mostly every game have it such as stamina regen, ranking, gacha. Please help, my game was on google play for 1 week plus, some players of follower was asking for ios. google play link : https://play.google.com/store/apps/details?id=com.bubluestudio.beyondgod

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

I recently had my Apple Developer Account removed from the App Store. I have spent 3 months trying to reach someone at Apple who can clarify the issue and help reinstate our developer status. No one has responded to us, explained the situation, or reviewed the case. I was able to get in contact with an old Apple App Store executive. After hearing the story, he agreed the situation seemed wrong. However, he no longer has connections at Apple, so he wasn’t able to help us. The app had millions of users and 50,000+ five-star reviews. Resolving this would allow us to restore the app and continue launching new products. Right now I’d appreciate anyone’s thoughts or guidance on this situation. Thanks!

Hello, I would like to ask the App Review team to look into a first submission that has not moved for nine days. Apple ID: 6792008109 Platform: iOS Submission: version 1.0, submitted August 30, 2026 Current status: Waiting for Review (has never transitioned to In Review) There is nothing pending on my side: No rejection and no message in the Resolution Center No metadata issue flagged No request for additional information Agreements, Tax and Banking complete App Privacy completed and working demo credentials provided I have also submitted an expedited review request through the Contact Us form. I understand review times vary with submission volume, and I am not asking to skip the queue. I am asking for visibility on whether this submission is queued normally or sitting in an error state, since nine days with no transition is well outside the expected range. Could the App Review team please investigate? Thank you.

We are a team of developers, and our company is involved in creating mobile applications. Recently, our developer account was terminated, and all active apps were removed from the App Store. The email mentioned that our app violates section 3.2(f) of the Apple Developer Program License Agreement. We've been trying to identify the issue since then, but we're not involved in any fraudulent activities. Our company is facing a critical situation as it is essential for us to have the apps back on the App Store as soon as possible. We are unsure of how to proceed and would greatly appreciate any assistance or guidance. Thanks. Our app ID com.seriktes.kz App name Seriktes

Hi everyone, I submitted my app for App Store Review almost two weeks ago, and the submission has been stuck in “In Review” status ever since. I understand that review times can vary, but this seems significantly longer than the usual review period. There haven’t been any requests for additional information or clarification from the App Review team, and the status hasn’t changed during this time. Has anyone else experienced an unusually long review period recently? Is there anything I should do at this point, or is it best to continue waiting? I’d appreciate any advice or insight from developers who have experienced a similar situation. Thank you!

Hi all, My app has been stuck in the "Waiting for Review" status since August 13 (US Time), and today is August 23. It has been 10 days without any status updates or messages from the App Review team. App ID: 6800282515 Submission Date: Aug 13, 2026 Developer Support Request Submitted: Aug 19 (No response yet) Expedited Review Requested: Aug 20 (No response yet) Current Status: Waiting for Review Since both support inquiries and expedited requests haven't received a reply after several days, I am concerned there might be an internal system hold or communication breakdown regarding this submission. Could someone from Apple please look into this or advise if any additional documentation/action is needed from my side? Thanks for your help!

Hi, My first app has been stuck since 14 August. App Review asked for more information. I sent it all back the same day. An hour later they replied: "Thank you for providing this information. We will continue the review, and we will notify you if there are any further issues." That was three and a half weeks ago and I have heard nothing since. I asked in the same thread on 2 September, no answer to that either. It still says Unresolved Issues and I haven't touched the build or the metadata since 14 August. So five weeks after submitting I'm sitting here with an app I can't release and nobody answering. It's getting to me, I won't lie. How do you get a submission unstuck? Is there anything I should be doing on my side? BlissGuru, Apple ID 6793882449, submission ID f3b964a4-7fdd-4190-9958-db93fc19958e, submitted 31 July. Thanks, Vincent

I would like to report a serious and repeated pattern of potentially misleading and impersonating applications published on the Mac App Store under the seller/developer name Mihai Graure. This is not a complaint about one isolated app. The same developer has published multiple applications using the names, branding, interfaces, and visual presentation of major services including LinkedIn, Zoom, Google Drive, Twitch, X/Twitter, TikTok, Facebook, Instagram, and Gmail. Reported applications: Desktop App for LinkedIn https://apps.apple.com/us/app/desktop-app-for-linkedin/id6786838795?mt=12 Desktop App for Zoom https://apps.apple.com/us/app/desktop-app-for-zoom/id6796387421?mt=12 App for Google Drive & Docs https://apps.apple.com/us/app/app-for-google-drive-docs/id6792317542?mt=12 App for Twitch https://apps.apple.com/us/app/app-for-twitch/id6797809667?mt=12 Desktop App for X (Twitter) https://apps.apple.com/us/app/desktop-app-for-x-twitter/id6786838258?mt=12 App for TikTok https://apps.apple.com/us/app/app-for-tiktok/id6783051609?mt=12 App for Facebook https://apps.apple.com/us/app/app-for-facebook-%C2%BA/id6770487788?mt=12 Apps for Instagram https://apps.apple.com/us/app/apps-for-instagram/id6778116535?mt=12 Desktop App for Gmail https://apps.apple.com/us/app/desktop-app-for-gmail/id6770216468?mt=12 My main concern is the overall presentation of these apps to customers. The developer uses the names of globally recognized services directly in the app titles. A user searching for Gmail, Instagram, Facebook, LinkedIn, Zoom, TikTok, Twitch, Google Drive, or X could reasonably believe these are official desktop apps or apps authorized by the companies that operate those services. The concern is not limited to the names. The apps also appear to reproduce or closely imitate the official user interfaces, layouts, navigation, branding style, and visual presentation of the services they reference. The App Store screenshots appear identical or extremely similar to the official interfaces users already recognize. This combination can create a very strong impression of legitimacy: the official product name is used in the title, the screenshots closely resemble the real service, the UI looks like the official product, and the app is presented as a dedicated “Desktop App” or “App for” that service. I specifically request that Apple compare the screenshots and the actual installed apps side-by-side with the official websites and applications of the corresponding companies. Apple should verify whether the developer has authorization to use these product names, trademarks, branding, interface elements, screenshots, layouts, graphics, and other protected material. Some listings may contain a non-affiliation statement, but this appears only at the end of the description, after the customer has already seen the app name, icon, screenshots, branding, and official-looking UI. In my view, a statement buried at the end of the description does not remove the misleading impression created by the rest of the listing. Many customers make download decisions from search results, titles, icons, screenshots, and the first part of a description. Apple should therefore review the complete presentation rather than treating an end-of-description disclaimer as sufficient where the rest of the listing may strongly imply official affiliation. This also appears to be a systematic developer-account-level pattern. The same seller has published at least nine apps targeting unrelated major brands operated by different companies, including Microsoft/LinkedIn, Zoom, Google, Amazon/Twitch, X Corp., ByteDance/TikTok, and Meta. The repeated strategy appears very similar across the portfolio: use the established service name, present the product as a dedicated desktop app, and reproduce or closely resemble the official interface and visual identity. Because the same pattern is repeated across many unrelated brands, I ask Apple to investigate the entire developer account rather than reviewing each listing in isolation. I believe these apps warrant investigation under App Review Guideline 4.1 — Copycats, as well as any applicable rules concerning intellectual property, misleading metadata, impersonation, trademark use, spam, and developer conduct. Please investigate whether: the apps impersonate or closely imitate established services; another company’s brand or product name is being used without authorization; the UI substantially reproduces the official product experience; App Store screenshots reproduce or closely imitate official interfaces; users could reasonably mistake these apps for official or authorized products; the developer has permission from each affected company; protected trademarks, graphics, layouts, screenshots, or visual assets are being used without authorization; this represents repeated copycat or misleading behavior across one developer account; the overall presentation is designed to benefit from confusion with established brands. I respectfully request that Apple App Review, Trust & Safety, and the appropriate Developer Program enforcement team conduct a full investigation of this developer account and all associated apps. Please review the actual installed applications, not only the written descriptions. The UI, screenshots, naming, branding, and full customer experience are important when determining whether these apps are misleading or impersonating legitimate services. Apple should also require the developer to demonstrate valid authorization from the companies whose names, products, and visual identities are being used. If Apple determines that these apps involve unauthorized brand use, repeated impersonation, copycat behavior, misleading presentation, intellectual-property misuse, or other Developer Program violations, I request removal of the affected applications and appropriate account-level enforcement, including termination of the Apple Developer Program account if warranted. This appears to be a repeated pattern involving multiple major brands, not an isolated naming mistake. I therefore ask Apple to investigate the complete developer portfolio and take appropriate action to protect Mac App Store users and preserve trust in App Store search results and developer identity.

I am new and submitted an app which got reviewed twice over the last 2 weeks. I tried adding IAP in the 2nd submission but it didn't get attached. I created 3rd submission and the status says Ready for Review. The IAP says (Unable to Submit for Review To submit your items for review, add an app version for the selected platform.). There is no option to cancel the submission and restart. Previous review cycles showed "Waiting for Review" and "In Review" before I got response on reasons for rejecting the app submission. But now it appears to be stuck. I requested email support. Is there any solution that I am missing? Thanks for your help! Raja

I'm building a custom keyboard extension that offers voice dictation. Because keyboard extensions are constrained (memory cap ~30–48 MB, restricted audio session access), I delegate recording to my container app: User in a host app (e.g., Safari) taps the mic in my keyboard extension. The keyboard calls extensionContext.open(URL("myapp://dictation")) to launch the container app. The container app records audio via AVAudioEngine + SFSpeechRecognizer, writes the final transcript to the App Group, and signals completion via a Darwin notification. 4. The user is expected to be returned to the original host app (Safari) automatically so they can keep typing. The problem (step 4): On iOS 26.4 I can no longer identify which app was the host. Every previously-known path returns nil for the keyboard extension's host: parent.value(forKey: "_hostBundleID") → returns the literal string parent.value(forKey: "_hostApplicationBundleIdentifier") → returns NSNull xpc_connection_copy_bundle_id on the underlying XPC connection (via PKService.defaultService.personalities[…]) → returns NULL NSXPCConnection.processBundleIdentifier on extensionContext._extensionHostProxy._connection → returns nil proc_pidpath(hostPID, …) → EPERM from the keyboard sandbox LSApplicationWorkspace.frontmostApplication → selector unavailable from the extension RBSProcessHandle.handleForIdentifier:error: → returns an RBSServiceErrorDomain error Without the host's bundle ID, the container app has no way to call LSApplicationWorkspace.openApplicationWithBundleID: (the technique that worked on iOS 25 and earlier). UIApplication.suspend() correctly sends the container to background, but iOS treats us as a "fresh launch" — it returns the user to the Home Screen instead of Safari, because the container app was launched by an extension, not directly by Safari. KeyboardKit's maintainer reached the same conclusion (issue #1014) and shipped 10.4 without the feature. My questions: Is there a public, App-Store-safe API in iOS 26+ for a custom keyboard extension to identify its host application, or for the container app (launched via the extension's openURL) to identify which app initially hosted the extension that opened it? UIOpenURLContext.options.sourceApplication reports the extension's own container, not the actual host. 2. Is there a public mechanism for "return to source app" when the container app was launched by an extension's openURL? Equivalent to the ← Source affordance iOS shows for normal inter-app openURL, but triggered programmatically by the launched app. 3. Some popular keyboards (e.g., 微信输入法 / WeChat Keyboard) still appear to round-trip through their container app on iOS 26.4 and return the user to the original host — including the iOS ← WeChat back affordance in the host's status bar afterward. What's the recommended approach to achieve this? If it requires a specific scene-activation flow, NSUserActivity pattern, or extension-context configuration, please point at the relevant docs. 4. If there is no public path today, is FB22247647 (or a related radar) the right place to track this? Should developers in this position migrate to in-extension audio capture (which has its own significant constraints in keyboard extensions)? I'd much rather not rely on private APIs. Concrete guidance — or even an acknowledgment of which direction Apple intends — would help thousands of custom-keyboard developers who currently have a degraded voice-input experience on iOS 26.4+. Tested on iPhone 12 Pro Max running iOS 26.4.2 (build 23E261), Xcode 26.x, Swift 5. Thanks!

Calling AppStore.requestReview(in:) with a valid, foreground-active UIWindowScene never presents the rating/review sheet on iOS 27 Simulator. The identical code works correctly on iOS 26 and earlier Simulator runtimes. Repro: if let windowScene = UIApplication.shared.connectedScenes .compactMap({ $0 as? UIWindowScene }) .first(where: { $0.activationState == .foregroundActive }) { AppStore.requestReview(in: windowScene) } Fresh Simulator install (Erase All Content and Settings first, to rule out the 3-per-365-day throttle). Run on iOS 27 Simulator → no sheet appears, no error, no console output. Run the identical build on iOS 26 Simulator → sheet appears as expected. Also tried: The SwiftUI @Environment(.requestReview) action (RequestReviewAction) instead of the UIKit windowScene call — same result, no prompt on iOS 27 Simulator. Ruled out an Xcode/Simulator-runtime version mismatch: reproduces both with an older Xcode + separately-downloaded iOS 27 runtime, AND with the matching Xcode 27 beta + its bundled iOS 27 Simulator. Checked the iOS 27 beta release notes — no mention of requestReview/StoreKit review prompt changes. Environment: Xcode [fill in version/beta] iOS 27 Simulator (beta [fill in]) Simulator device: [e.g. iPhone 16] Expected: Review prompt presents (subject to the documented frequency limit), matching iOS 26 behavior. Actual: No prompt, no error, on both the UIKit and SwiftUI review-request APIs.

Hi everyone, I’m a developer maintaining an existing app that has been live on the App Store for many years. We regularly submit updates, and normally our submissions are reviewed and approved within 48 hours without any issues. However, I’m currently experiencing an unusual situation and would appreciate some advice. 19 August: I submitted a new version of the app. It went into review but was rejected under: Guideline 1.1 - Safety - Objectionable Content The app’s marketing includes terms or images that reference objectionable content or services. These references can be found in the app’s metadata, including, but not limited to, the following metadata field(s): description and name. I’m not sure what triggered this rejection because the app name and description have not been changed for years. The app has been live and regularly reviewed during that time without this issue. The rejection also did not identify the specific wording or content in the app name or description that was considered objectionable. I responded to the review team explaining the situation and asked them to identify the specific part of the metadata that caused the issue so that we could review and update it if necessary. However, I did not receive any further response. I also submitted an appeal, but I have not received a response after several days. 21 August: Because we still need to maintain the app and release updates, I cancelled the previous submission and submitted a new version for review. However, this submission has also remained pending and has not moved forward to review. 25 August: I cancelled the submission again and created another submission containing both maintenance updates and a big launch for a new country. This update is important for our business because the new operation is scheduled to launch on 1 September. We need the app update to be reviewed and approved before then. I have also submitted an expedited review request and a new ticket, but it still hasn’t moved forward or been reviewed. My questions Is there anything I can do to get the current submission reviewed, given that the previous submission was rejected and the appeal has not received a response? Could the previous Guideline 1.1 rejection be causing the subsequent submissions to remain pending? Should I continue waiting for the current submission, or is there another recommended process for escalating this situation? The delay is now becoming critical because the new country launch is scheduled for 1 September, and not having the required app update available by then would significantly affect our business operations. Any advice from other developers who have experienced a similar situation would be greatly appreciated. Thank you.

Hello, since July 31st, our app has been stuck in the waiting for review state for a long period of time. We have already taken some actions. July 31: first submission. August 10: after waiting for over a week, we assumed there was a problem with the review queue -> cancel and resubmit. We attempted to submit an expedited request, but there was an issue with Apple service. It keeps saying "Sorry, we didn't receive your request." August 13: request a call with the Support Team. There was a guy named Tony who answered. Unfortunately, even Apple's staff is unable to access their internal system, as he told us that, and "he don't know why"? August 14: request a call again. Apple staff - Andy took up the phone and said he could not do anything about this situation and said... We just have to wait. August 25: rejected the build, upgraded the version, and submitted once more. We're hoping that this build will get out of the stucked queue... Side notes: Attempted to submit another expedited request were unsuccessful, the problem remained, tried several times. Made an appointment for a App Review team. But even the registration is still pending. Does anyone here have suggestions or solutions for this situation? This is the first time we've encountered this situation, and it's quite strange. Isn't that a side effect of the August 8th maintenance?

Dear all, Is there any way to contact Apple dev team by phone ? They aren’t responding to mails, neither by messages from the App connect. It’s been 2 weeks and still no update and now the deadline is reaching tomorrow. Anyone can help please ?

Hello Apple Developer Community and Apple Support Team, We are seeking guidance regarding our Apple Developer Program account (Account Holder: Rami Waleed Mohamed Gallo), which was closed under Section 3.2(f) on August 23, 2026. We deeply respect the App Store Review Guidelines and the standards Apple sets to keep the ecosystem safe and trustworthy. We take these rules very seriously. Following our Notice of Termination, we submitted a formal appeal to the App Review Board and provided detailed clarification regarding our applications and operations. Our account has been closed since August 23, 2026, and we have not yet received a status update or guidance regarding our appeal (Reference Case ID: 20000149214883). We have been a dedicated member of the Apple Developer Program for over 4+ years, managing over 25+ applications serving active corporate clients (including enterprise logistics, automotive, and healthcare applications) and thousands of daily active users. The account termination and loss of backend services (such as push notifications) is causing severe operational disruption for these businesses and end-users. We are fully committed to cooperating with Apple, providing any requested business or identity verification documents, and implementing any necessary compliance processes to resolve this matter and rebuild trust. We would be extremely grateful for any guidance from the Apple Team or the community on: Identifying the specific application, incident, or action that led to the termination, so we can address and fix the root issue immediately. How to confirm our appeal and materials are under active review by the App Review Board. Any additional steps or escalation paths we can take to clarify this situation. Thank you for your time and assistance. Account Name: Rami Waleed Mohamed Gallo Support Reference Case ID: 20000149214883